-
Notifications
You must be signed in to change notification settings - Fork 39.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wait for the job to be removed #64439
Conversation
By("verifying the job " + jobName + " was deleted") | ||
_, err := c.BatchV1().Jobs(ns).Get(jobName, metav1.GetOptions{}) | ||
_, err = c.BatchV1().Jobs(ns).Get(jobName, metav1.GetOptions{}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So we can use _, err = framework.WaitForJobGone(c, ns, jobName, 0)
here, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I guess we could, but I've just backported what we have in master right now.
/retest |
[MILESTONENOTIFIER] Milestone Pull Request Labels Incomplete @MaciekPytel @deads2k @soltysh Action required: This pull request requires label changes. If the required changes are not made within 3 days, the pull request will be moved out of the v1.10 milestone. kind: Must specify exactly one of |
This is the equivalent of the e2es we have in master that do the "wait for GC" now, right? /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, soltysh The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Yup |
/retest |
/test pull-kubernetes-e2e-kops-aws |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue. |
What this PR does / why we need it:
In master we've dropped reapers (#63979) which means the old client does not wait long enough for the resource to be gone (since it's being removed on the server along with its dependents). To fix our e2e (failure here) we need to backport parts of the aforementioned PR which is updating tests to wait for the resource to be removed.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #64362
/assign @MaciekPytel
/assign @deads2k
Release note: